Monster Media 1996 #15

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1996 #15 / Monster Media Number 15 (Monster Media)(July 1996).ISO / bbs_util / transx11.zip / TX.DOC < prev next >

Wrap

Text File | 1996-05-22 | 50KB | 1,155 lines

▄▄ ▄▄ ▀▀▀▀█▀▀▀▀ █▀▀▀▀▀▀▄ ▄▀▀▀▀▀▀▄ █▄ █ █▀▀▀▀▀▀ ▀█▄ ▄█▀ █ █▀▀▀▀▀▀▄ █▀▀▀▀▀▀█ █ ▀▀▄▄ █ ▀▀▀▀▀▀█ ▐█▌ █ █ █ █ █ █ ▀█ ▄▄▄▄▄▄█ ▄█▀ ▀█▄ ▄█▀ ▀▀ ▄█▀ v1.1 Internet/Fidonet Transporter ▄█▀ Copyrighted Multiboard Communications Centre, 1995-1996 All rights reserved ▄█▀ ▄█▀ ╓────────────────────────────────────────────────────────────────────────────╖ ║ Introduction ║ ╙────────────────────────────────────────────────────────────────────────────╜ What is it? ■ An inexpensive solution to the high cost of running long-distance fidonet comaptible connections. ■ Transx is, in essence, a fidonet mail tosser that uses internet email as a transfer medium rather than requiring you to call the remote system directly to transfer mail. Is it secure? ■ It has integrated error checking, and loss prevention methods, as well as security features to ensure the safe unaltered delivery of your mail. How does it work? ■ What it does is scan through your netmail directory, looking for mail destined to sites you have setup in your connections list. Upon finding any, it will encode the mail and any attached files and send them to the remote site via email. The remote site would then use Transx to decode these messages back into their original state, just as if you had called directly and dropped them off. How much work is it to run and maintain? ■ Once setup, this send and receive transfer process is fully automated and runs much like your echomail processor does. ╓───────────────────────────────────────────────────────────────────────────╖ ║ Installing ║ ╙───────────────────────────────────────────────────────────────────────────╜ Installing Transx couldn't be simpler. 1) Simply extract the archived package into the directory you wish to keep Transx. (It is HIGHLY suggested you choose a new directory for this, since it will create two subdirectories of its own) 2) Run TXSETUP.EXE, it will give you the option of running quick setup, or if you choose not to use the quick setup, the setup program will continue normally and allow you to manually edit the information. Now you need to integrate it with your current email system. If you are using a direct UUCP connection then follow the UUCP Install instructions, otherwise skip down to the netmail install instructions. UUCP Install ■ This is the easiest and most efficient method of running Transx, as Transx can directly read/write to your UUCP spool bypassing any netmail conversion steps. ■ Here are the important things to do when setting up the UUCP. 1) Run TX.EXE in an event periodically to make sure that is run often. Optionally you could place it in the batch file you use to call your internet provider. For example: TX.EXE /NOIMPORT DIALUUCP TX.EXE /NOEXPORT ..would be a pretty efficient way to run Transx. 2) Make sure that messages to "transx@yoursite.com" are never imported into your BBS. If for some reason Transx misses a message (due to network error, or file locking) and your internet email tosser imports the mail for Transx into your BBS, then Transx will never be able to process that message since it will be removed from the spool after it was imported to your BBS. If you are using NetXpress you could prevent this by running Transx from a SERVICES.IN setting.. SETUP.EXE -> Configuration -> Special Files -> SERVICES.IN ┌ Special File: SERVICES.IN ─────────────────────────────── │ Service Name Batch Filename ├────────────────────────────────────────────────────────── │ transx m:\transx\tx.exe │ Almost all internet tossers should have some sort of option to hold the importing of a message into your BBS, or to run a service when it sees mail to a certain user. Consult your UUCP mail processor documentation if required. Netmail Install ■ This method allows compatibility with almost every fidonet compatible system that uses netmail for it's internet email. Either this mail is processed by a netmail/email converter on your site, or perhaps from a local provider. ■ Here are the important things to do when setting up.. 1) Run TX.EXE in an event periodically to make sure that is run often. Putting it in your "Mail Received" batch file is not usually sufficient for most systems, since if you do not receive mail for a while, Transx will not be run, and your mail will not be exported via Transx. One solution is to add it to your nightly maintenance batch file in addition to placing it in your "Mail Received" batch file to ensure that it is run at least once a day. 2) Make sure that messages to "Transx" are never imported into your BBS. If for some reason Transx misses a message (due to network error, or file locking) and your internet email tosser imports the mail for Transx into your BBS, then Transx will never be able to process that message since it will be removed from the spool after it was imported to your BBS. The best way to do this is by going into your echomail tosser and adding "Transx" as a user, and then specifying your echomail tosser to not import mail for this user into your netmail directory. For GEcho, you can do it like this: GSETUP.EXE -> System Data -> System Users ╒═════════════════════════════════════════════════════ 2 ╕ │ │ │ SysOp name Transx │ │ Personal mail area 0 │ │ Use AKA area No │ │ Netmail area 0 <---------------------------------- │ │ ╘═════════════════════════════════════════════════════════╛ For FastEcho, you can do it like this: FESETUP.EXE -> System -> Users ╔════════════════ Users ════════════════╗ ║ Name ║ ╟───────────────────────────────────────╢ ║ 1 Pete Rocca ║ ║ 2 Transx <-------------------------------------------- ║ 3 ║ ..and.. FESETUP.EXE -> System -> FEUTIL parameters ┌───── FEUTIL parameters ────┐ │ PURGE - Messages 0 │ │ Days 0 │ │ Rcvd Days 0 │ │ Use arrival date Yes │ │ Autorenumber at 0 │ │ Exclude Users Yes │ │ Exclude SysOps Yes │ <----------------------------- For FastEcho both of the above have to be active. If you still wish to have your personal mail imported into the BBS netmail rather than left in the netmail directory, you can remove your name from the list of "Users" and FEUTIL Import will import your mail but leave Transx mail alone. Also, if you are running iServer, you can incorporate an Infobot to run Transx when mail comes in for it.. ISERVCFG.EXE -> Infobot Response System ╔══╡ Infobot Response System ╞═════════════════════════ ║ ║ TRANSX Delay M:\TRANSX\TX.EXE ╔══╡ Edit ╞═════════════════════════════════════════════╗ ║ ║ ║ Trigger : TRANSX ║ ║ Type : Delay run ║ ║ File : M:\TRANSX\TX.EXE /NOEXPORT ║ ║ Subject : ║ ║ ║══ ╚═══════════════════════════════════════════════════════╝ Ensure that you have iServer setup for "Delay run", as if you have it set for "Run program", you will lose mail due to type of interaction required. Even if you are using iServer, it is a good idea to make sure that you use the GSETUP/FESETUP method to make sure that your mail is 100% safe from being imported to the BBS accidentally. ╓────────────────────────────────────────────────────────────────────────────╖ ║ TX.EXE - The main program ║ ╙────────────────────────────────────────────────────────────────────────────╜ TX is the program that you run in order to process the inbound and outbound mail for Transx. There are a number of command line parameters that you can use to change aspects of the default properties, or to run statistical tools and informational reports. To run it in normal mode, no command line parameters are required. ■ Commands and options /NOEXPORT - Do not encode outbound mail /NOIMPORT - Do not decode inbound mail /NOLOGO - Disable the Transx logo upon startup {+} /NOAUTO - Disable automaintenance /MAINT - Force maintenance /STATS - Display current traffic statistics ■ Queue reporting and management /DETAIL - List a detailed report on queued/held messages /SUMMARY - List a summary report on queued/held messages /KILL - Delete the queued/held messages /EXPIRE - Expire the queued/help messages Modifiers /FOR:[user] and /FILE:[filespec] can also be used to limit the processing on only matching criteria For example, to expire all held messages for a connection at "transx@remote.sys" you could use something like "TX /EXPIRE /FOR:remote.sys" For more information about how and where to run TX.EXE from, please refer back to the "Installing" section of the documentation. ╓────────────────────────────────────────────────────────────────────────────╖ ║ TXSETUP.EXE - The setup and configuration program ║ ╙────────────────────────────────────────────────────────────────────────────╜ TXSETUP is a fully windowed setup program with a complete online manual to help you get things running with as much ease as possible. The setup program has the following main options... General Information └───────────────────────────────────── Sysop ■ This is where you put your name, or the name of the person who will be administering Transx on your system. This name is used in coding and for report generating. System name ■ This is where you put your system name which is used in identifying your system, and writing organization information in the UUCP spools. Domain ■ This is your internet domain address, it is used both for the sending and receiving of mail, as well as a used in creating unique message identification lines. Site address ■ This is the netmail address that inbound internet email messages are addressed to. If you are using the direct UUCP spool options, then just use your main system netmail address. Site address .. Aka ■ For the best integration with your current mail setup, it is quite important that you enter all of your system aka addresses here. These addresses are used to determine which messages to classify as "InTransit" Gate address ■ This is the outbound address that you send your internet email to. For example, if you send your outbound email to 1:2401/305.5, then place this address in here. If you are using the direct UUCP spool options, then just use 0:0/0. Gate netflags ■ Here you can specify the netmail flags that outbound translated mail addressed to your UUCP host should have. Kill/Direct is a common standard. Robot name ■ This is the robot name that Transx will look for incoming mail to be addressed to. The given standard is "transx" but if you require to change it, you may do so here. ■ This name is used in conjunction with your domain name and should be used by your connections as the Transx address to send to. ■ For example a domain name of "yoursite.com" and robot name of "transx" would give you a Transx address of "transx@yoursite.com" This address would be what your other connections would use to export their outbound mail to. Serial and Registration ■ This is where you put your serial and registration numbers once you have registered this package. File and Path Configuration └───────────────────────────────────── Log file ■ Here you can define the log file you wish to have updated with logged information. If you do not wish to have a log file, simply leave this field blank. Netmail path ■ This is where your *.MSG files are located. This will be the directory that is scanned for outgoing mail waiting to be converted and sent via Transx. ■ Also, if you are not using an advanced spool, Transx will use this path to create it's outbound *.MSG files, destined to your UUCP gateway. Update semaphore ■ These are files that you can update or "touch" when Transx has modified the netmail directory. They are typically good for causing other tasks to rescan the modified messages. For example... M:\FD\FDRESCAN.NOW (FrontDoor) M:\DB\DBRIDGE.RSN (D'Bridge) Secure inbound ■ This is the directory to place inbound files that were decoded and included a secure envelope. A secure password can be configured in the Connection Manager section of the setup program. Inbound files can include file attaches and inbound echomail bundles. ■ The secure setting is much like the "Secure session" that you can establish between mailers. Insecure inbound ■ This is the directory to place inbound files that had a valid envelope, but not listed as secure. Violation inbound ■ This is the directory to place inbound files that did not have a valid envelope, or had an unexpected or incorrect secure password used. ■ It will also be the directory that files are moved into if the message had a valid insecure envelope, but you have the system marked as "Secure inbound only" in the Connection Manager setup. Default Options └───────────────────────────────────── Send acknowledgments ■ If you wish to send acknowledgments to remote sites not in your Connection Manager that send you mail, then select yes. ■ It is a good default to send receipts if you do not know if the remote site needs them, since if they are not required by the remote site, it will simply discard them. Send acknowledgments .. Expiry hours ■ This expiry setting determines how many hours you should keep parts of inbound files that are not yet completed before assuming the missing parts were lost and requesting a resend from the remote site. ■ Note that this value should be kept fairly small to ensure that you do not have mail lags if a part ever goes missing, however it should not be so short that it prematurely submits a resent request while the parts may be still in transit. A setting of 24 hours is probably sufficient for most systems. Accept resend requests ■ If you wish to hold on to sent mail for a number of days in order for the remote site to be able to re-request failed packages, or for auto-resending, then select yes. This setting applies to nodes that are not in your Connection Manager already, in which case the Accept resend requests there will override this setting. Accept resend requests .. Expiry hours ■ This expiry value determines how many hours to keep mail held incase of a remote resend request. Once mail has expired this time setting, it will be deleted. ■ Note that if this value is too short, some systems with slower UUCP connections may not send a resend request before you expire the mail. This value should typically be at least one day longer than the remote's Send acknowledgments expiry hours. Auto resend unacked mail ■ If you wish to, by default, automatically resend mail packets that you have not received an acknowledgment for, then select yes. This setting is usually best left off since you do not know if unknown sites (not listed in your Connection Manager) will be sending you acknowledgment receipts. Auto resend unacked mail .. Max resends ■ You can restrict the number of times any given message is resent from your system. This includes the remote re-requesting the mail and auto resends if setup. ■ This is can be used for either of two reasons, the first being that you might not want a site to become reliant on requesting the package 10 or 20 times just because they are losing packets due to setup or human problems, and it can also be used to stop endless resend loops if the remote system never sends an acknowledgment for the package. Decode stray inbound mail {+} ■ You can have Transx decode mail addressed to your robot name even when the remote site is not in your connections list. If mail of this type is decoded, it takes its properties from the Default Options configuration. ■ If you set this to "No" then sites not listed in your connections will not be able to send you Transx mail. Max length ■ This is the maximum length of each part of a multi-part file. For example, if you were sending a 100,000 byte file, and had this value at 30,000 bytes, it would send 4 parts to complete the file. ■ This value MUST be smaller than the smallest split point in the path between your system and the remote system. For example... If you were sending mail from site A to site C through site B, and site B's gateway splits messages at 30,000 bytes and site C splits messages at 40,000 bytes you would have to pick a number 30,000 bytes or less. ■ Very important! In other words, if any package other than Transx resplits the messages into smaller parts, the receiving Transx program will not be able to reconstruct the original message. ■ Default A good default is 15000 bytes or less, since it is the smallest default setting of any gateway that we currently know about. If you are setting up a connection with another site you can negotiate a higher setting for better efficiency, but for sites that you are not sure about (ones not in your connection table) using the 15000 byte setting is the best bet. If you get an error saying "? Invalid message; reason = 4" then chances are pretty good that the message was resplit by a gateway. Log Options └───────────────────────────────────── ■ You can specify how much information is written to the log file by toggling the Yes/No setting for each category. ■ The "Debug logging" option enables all the logging levels as well as logging skipped messages, and additional debug info to help isolate any problems you might encounter. Advanced Options └───────────────────────────────────── Kill empty inbound file attach messages ■ If you wish to delete inbound messages that are empty, rather than leave it in your netmail folder, select yes. These types of messages are typically for file attaching echomail bundles, and are normally removed by your mailer. Export messages marked Crash/Immediate ■ You may not want to translate outbound mail with Crash/Immediate status flags. If you do wish to export them regardless of these settings, select yes. Export messages marked Freq/Ureq ■ You may not want to translate outbound mail with Freq/Ureq status flags. If you do wish to export them regardless of these settings, select yes. Export messages marked Hold ■ Normally messages marked as "Hold" will not be sent, however if you wish to override this setting, select yes. Send sysop notification on bad packets ■ When a bad package is received, you can have Transx post you a message containing as much of the failed message as possible and, if available, the file that was attached. ■ If you have request receipts enabled, the package will be requested again from the remote site regardless of this setting. Advanced spool .. Type ■ Transx has the ability to increase efficiency by supporting different file formats for your messages. This allows you to bypass many steps required to send internet email depending on how your system is configured. ■ By default Transx uses the *.MSG format for both inbound and outbound mail. Messages destined to the internet are simply addressed to the gateway address specified in the General Information section, and left for your gateway/tosser/packer to deal with. However, if you are running the gateway yourself (rather than using a remote fidonet compatible system to transfer email) you can bypass a number of steps that are typically required to process internet email from a fidonet system. There are three types supported by Transx... None This is the standard method for delivering email via a netmail format to the internet and not considered to be an Advanced Spool. Outbound mail.. Your system (*.MSG) Netmail destined to gateway address Fido tosser (*.PKT) Compressed packet Gateway (*.DAT) UUCP -> Internet Inbound mail.. Gateway (*.D/X) Internet -> UUCP Fido tosser (*.PKT) Compressed packet Your system (*.MSG) Netmail from gateway address PKT This is similar to the above routine, except with outbound mail, it skips the *.MSG step, and directly creates the compressed packets (*.PKT) for your gateway program to export, saving your echomail tosser from having to do that job. UUCP This is the most efficient method for using Transx if you have a direct UUCP feed. It bypasses all the conversion steps and reads/writes directly to your UUCP spool directory. If you have a direct UUCP feed it is highly recommended to use this spool type. If you are using this method, no 3rd party utilities other than your UUCICO transfer program are required to use Transx. SMTP This is the most efficent method for using Transx if you have a direct SMTP server. It bypasses all the conversion steps and reads/writes directly to your SMTP spool directory. Advanced spool .. Path ■ If you are using the Advanced Spool Type of PKT Type 2+, then this should be the directory that your gateway program looks for *.PKT files to export. ■ If you are using the Advanced Spool Type of UUCP (In/Out) then this should be the UUCP spool directory for your site. Note that this is NOT the spool root directory, rather the actual path that the *.D/*.X files can be located, as well as the correct path to write outbound *.DAT/*.XQT/*.CMD files. ■ If you are using the Advanced Spool Type of SMTP then the in and out paths defined should match the paths used by your SMTP server. UUCP options .. Site name ■ If you are using the advanced UUCP spool, then this is your site name as your UUCP host knows you. This is not always the same name as your domain name, and should match the "uucpname" setting in your UUCICO transfer program. UUCP options .. Host name ■ If you are using the advanced UUCP spool, then this is your UUCP hosts name. This is not always the same name as their domain name, and should match the "hostname", "dialing name" or "remote name" setting in your UUCICO transfer program. UUCP options .. Time zone ■ This is your difference in time from UTC. This is used in the generation of time stamps for outbound UUCP mail. The time is usually plus or minus the number of hours and minutes in the HHMM format. For example... If you are in the Eastern Standard Time zone (which is UTC minus 5 hours), then the value should be -0500. You can also override the value that gets placed as the time zone when posting the packets, by setting the TZ or TZUTC environment varibles. This is designed to make configuration easier for those locations in which the time zone varies during the year. Notes... ■ If you are not running a gateway yourself, rather calling out to another system to deliver netmail-style internet messages, then you MUST use the setting "None" for Advanced Spool Type. Connection Manager └───────────────────────────────────── This is where you define your "Connections" whom with you will be using Transx to communicate with. This is remarkably similar to setting up your connections in your echomail tosser. How do you know who to send to? Well, that's a lot like asking, where should I address my postal mail? or where do I drive to work? Your connections will depend on who you talk with, and who else wishes to run a Transx connection with you - it is something you setup within your network of contacts. For example, if you talked a great deal with someone long distance to you, and you both had email running on your board, you could both arrange to run Transx and exchange your connection info. You would then be able to eliminate your long distance between the two of you, saving both of you lots of money. Also, you can now take part in smaller fidonet style networks across the world, that would have been impractical or costly to do so before. Or if you host a network, here is your chance to make it international since it wouldn't cost your downlinks anything to carry it! Another method of getting Transx contacts, is to spread the word about Transx, perhaps add your Transx address in your signature file. The more people that have your address, the more can send to you, and you in return can get their information and send to them. Editing a Connection └───────────────────────────────────── Sysop ■ This is the name of the sysop/adminstrator at the remote site. Network address ■ This is the network address of the site that you will be sending to. Any netmail messages found in your *.MSG directory to this address will be considered for Transx export. Transx address ■ This is the email address of the Transx receiver on the remote system. (this is not the email address of the administrator of the remote site, rather the address which answers the Transx mail) ■ For information regarding "robot name" please reference the help in the General Information setup screens. Password ■ If you wish to have a secure envelope added to the message, you can do so by specifying a password here. A secure envelope means that the contents of the message have not been altered during transport. Both you and the receiver will have to use the same password or you will receive "Invalid password" notices. Max length ■ This is the maximum length of each part of a multi-part file. For example, if you were sending a 100,000 byte file, and had this value at 30,000 bytes, it would send 4 parts to complete the file. ■ This value MUST be smaller than the smallest split point in the path between your system and the remote system. For example... If you were sending mail from site A to site C through site B, and site B's gateway splits messages at 30,000 bytes and site C splits messages at 40,000 bytes you would have to pick a number 30,000 bytes or less. ■ Very important! In other words, if any package other than Transx resplits the messages into smaller parts, the receiving Transx program will not be able to reconstruct the original message. Translate outbound ■ If you wish to use Transx to export outbound messages to this site, select yes. If you wish to only accept inbound from this site, or wish to suspend mail for a short period, you can disable translating outbound mail. Translate inbound ■ If you wish to decode inbound mail from this node, then select yes here. If you do not want to decode inbound Transx messages for any reason, you can do so by selecting no. Secure only ■ If you have a secure session password with this remote node, and wish to flag messages that are not password encoded as "Invalid password", then select yes, otherwise mail will be processed normally whether the remote site is using the password or not. Send acknowledgments ■ If you wish to send acknowledgments to the remote site when you receive your mail, then select yes. This should usually match the remote setting for "Accept resend requests" ■ You can also select "Batch" which means that multiple receipts to the same site in the same session will be sent in one message rather than a single message per receipt. Send acknowledgments .. Expiry hours ■ This expiry setting determines how many hours you should keep parts of inbound files that are not yet completed before assuming the missing parts were lost and requesting a resend from the remote site. ■ If set to zero then it will take the value from the "Default Options" setting. This field is great if you need to have different expiry hour settings for different nodes. Accept resend requests ■ If you wish to hold on to sent mail for a number of days in order for the remote site to be able to rerequest failed packages, or for auto-resending, then select yes. This setting should usually match the remotes "Send acknowledgments" setting. Accept resend requests .. Expiry hours ■ This expiry value determines how many hours to keep held mailing waiting before expiring it. ■ If set to zero then it will take the value from the "Default Options" setting. This field is great if you need to have different expiry hour settings for different nodes. Auto resend unacked mail ■ If you wish to automatically resend mail packets that you have not received an acknowledgment for, then select yes. You should only use this setting if you have "Accept resend requests" turned on and the remote system is sending you acknowledgments. Notes... ■ The acknowledgment/resend features of Transx allows you to ensure safe mail delivery over the internet without little or no chance of any problems or mail loss along the way. ■ If both systems are using the acknowledgment/resend features, you know that mail will be resent if it doesn't get acknowledged by the other side. You may, however, decide that the mail is either not important enough, or that your link is secure enough to not require to use these features to ensure safe mailing. Routing (Commercial version only) └───────────────────────────────────── ■ Transx has the ability to route and send mail via another Transx user, acting as a Gateway, to another site who may not have Transx setup themselves. For example... If you were routing all mail to Zone 99 via 99:1/0, you would have an entry for your connection with 99:1/0, but in addition, you would insert a routing entry of "99:*", which would route all mail to Zone 99 to 99:1/0, who would then decode it as normal netmail, and deliver it to the intended recipient. Gateways can forward to other gateways, and so on, which makes Transx an excellent method for moving mail quickly and inexpensively. ■ Transx is "smart" when routing, and will always try to pick the most direct connection when routing conflicts are found. For example... Say you were sending a message to 99:400/123, and you had two connections setup that routed mail to Zone 99... 1) 99:1/0 - that routed mail for 99:* 2) 99:400/0 - that routed mail for 99:400/* The message would be Transx sent to 99:400/0 since it contains a higher level destination match and is probably physically closer or quicker to the destination. ■ You can also exclude addresses from being routed by placing a minus sign before the routing entry. For example... You could have the following routing entries: 1) 99:4* 2) -99:400/* This would cause all routable messages for 99:4*/* to be routed with the exception of messages addressed to 99:400/* ■ By default, Transx will not route messages with files attached to them, however if you if you have a connection that permits you to route messages with files through them, you can add the ",F" suffix to the route entry.. For example... You could have the following routing entries: 1) 99:1/* - would route mail to 99:1/* via the connection 2) 99:1/*,F - would route mail even with files via the connection Notes... ■ Of course there are a few things to keep in mind when setting up your routing entries... * You must have an agreement with the gateway to allow this * You must have a connection setup to the gateway * The gateway should be closer to the destination than you are ■ You can qualify a system with an level of address matching. This means that addresses such as Zone:*, Zone:Net/*, Zone:Net/Node.* or exact address matches are all valid. When specifying point 0, do not include it in the addressing, for example 1:2401/305.0 should read "1:2401/305" without the ".0" ╓────────────────────────────────────────────────────────────────────────────╖ ║ TXUTIL.EXE - The utility program ║ ╙────────────────────────────────────────────────────────────────────────────╜ Included with the commercial version of Transx is TXUTIL, a program which allows you to view and/or alter the settings of queued Transx packets. Below is a list of features available in the utility program. ALT-D - Delete this package ALT-E - Expire this package ALT-Q - Requeue this package into the netmail directory ALT-R - Send request for remote to resend this package ALT-A - Send receipt acknowledging this package F10 - Rescan packages ALT-N - Sort packages by remote address ALT-T - Sort packages by expiry time T - Tag all packages U - Untag all packages SPACE - Toggle package tag status ? - Description of flag settings Notes... ■ The shareware version of this utility program only allows you to view the message and message settings, you will not be allowed to modify the message settings. ╓────────────────────────────────────────────────────────────────────────────╖ ║ Common Questions ║ ╙────────────────────────────────────────────────────────────────────────────╜ Q) What do I need to run it? * You'll need to be able to have either a UUCP account or be able to receive email as netmail messages via some type of email gateway. * In order for communication with another system, they too will be required to be running the Transx package. Q) How does it work? * Basically it scans your netmail folder for outgoing mail to another Transx site, it encodes the mail and sends it along with security and confirmation information as email. * It is received on the other end and decoded back into its original format, whether it would be netmail, echomail or file attaches.. * If mail is lost or damaged in transit, it can automatically recover by the use of acknowledgement receipts. Q) It is not sending out mail to one of my connections? * Make sure that the message does not have the Lock/Hold status flags, or if it has the Crash/Immediate flag, make sure that you have TXSETUP configured to allow the exporting of immediate mail in the Advanced Options section. * Make sure that you have "Translate Outbound = Yes" setup for this system in the Connection Manager. Q) What do the status numbers mean when doing a /SUMMARY report? * If you do a /DETAIL report, it will give you a text description for the status number, however here is a breakdown of what the numbers mean if you do not want to do the /DETAIL report. # Error Cause ─── ─────────────── ──────────────────────────────────────────── 0 None No error has occurred 1 File error Could not find file attach (export) Could not create new file (import) 2 Write error Error occurred when writing new file 3 Bad message Message body was corrupted 4 Bad segment File segment data was corrupted 5 No message id Inbound message was missing an id tag Q) How large can the files be that Transx will send? * Transx can split and transfer any file in upto 1295 pieces, therefore if you are using a max length of 60000 bytes then the maximum file size you could send in a single file would be roughly 70 megabytes. Q) Do I have to add TX /MAINT to my nightly maintenance? * You can run TX /MAINT as often as you like, however if you don't run it for more then 24 hours, TX will perform maintenance the next time it is run, so no, it is not required, but you can if you want to make sure it is only run at a certain time. Q) Routing doesn't seem to be working, it sees the messages that I want to route, but doesn't pack them? * Make sure you are using the Commercial version. The Shareware version does not support routing. * Make sure that the messages do not have the Direct, Crash, Hold, Immediate, or Lock flags set, messages with any of those status flags are not qualified to be routed. * Make sure that you have a valid routing entry setup with a direct connection that matches the destination. Also make sure that this connection is setup to "Translate outbound", otherwise it will not be eligible to be a routing host for the message. ╓───────────────────────────────────────────────────────────────────────────╖ ║ Support ║ ╙───────────────────────────────────────────────────────────────────────────╜ If you have any questions or comments, you can netmail us at FidoNet address 1:2401/305 (CM,V34,VFC). Please poll back for your replies as we get dozens of messages a day or optionally make a note that you would like your message routed back to you. You can also contact us via the internet for faster responses, and directly sent out replies. The address is "support@multiboard.com" You can also find us in the RA_UTIL echo conference, as well as the MCC_SUPPORT echo of course. The newest MCC software is also available via the internet: http://www.multiboard.com ftp://ra.uti.com/sys/bbs/bbs/mcc ftp://pcmicro.com/4_authors/multiboard You can also "FREQ" the files from us via fidonet at 1:2401/305, our system is online and taking requests 24 hours/day. The magic name for the newest version is "TRANSX", or freq "CATALOG" for the newest list of our other products. You can help us direct your messages by using the alternative email addresses when posting us mail: (1) support@multiboard.com - general inquiries (2) sales@multiboard.com - registrations/commercial info (3) suggestions@multiboard.com - suggestions (4) reports@multiboard.com - bug reports Thanks for your interest and support! ╓───────────────────────────────────────────────────────────────────────────╖ ║ Registration ║ ╙───────────────────────────────────────────────────────────────────────────╜ There are two different versions of Transx currently available: 1) Shareware The shareware version is nearly identical to the unregistered evaluation version that you are testing, with the exception that it will allow you to have 2 connections instead of 1, as well as eliminate the unregistered notices and delays. This version is excellent for connecting to main Transx hubs to collect mail and files. If you are planning on having more than two connections, you should consider the Commercial version. To register this version, simply complete the correct registration form for your area and send it to that registration site. 2) Commercial/250 This commercial version comes with a disk and printed manual. It allows for upto 250 connections, as well as enables both message and file routing capabilities. It also includes the full-screen detailed queue modification and viewing program. This version is excellent if you plan on routing mail to save you money, or if you plan on connecting to more than 2 systems. Some good examples would be: ■ Network Co-ordinators for fidostyle networks ■ Software authors for their beta teams ■ Companies with internal fidostyle mail systems ■ Leaving yourself free for future expansion The cost for registering the commercial/250 node version is $60 US, and that includes the disk and printed manual. For information about the closest commercial registration site to you, please contact us at: ■ reginfo-transx@multiboard.com - For a listing of commercial registration sites and other product information. ■ support@multiboard.com - To contact a staff member about a problem or for more information about Multiboard software. ■ Fidonet at 1:2401/305 (V34,CM) - To contact a staff member about a problem or for more information about Multiboard software. ■ Postal at Multiboard Communications Centre 363 Colborne Street, Suite 1501 London, Ontario N6B 3N3 For systems requiring more than 250 connections, please contact us for information about our extended commercial packages. ╓───────────────────────────────────────────────────────────────────────────╖ ║ License and Disclaimer ║ ╙───────────────────────────────────────────────────────────────────────────╜ "Transx" is NOT free, it is being marketed under the "try before you buy" or the shareware concept. You are entitled to use Transx for a period up to thirty (30) days, after which you MUST register or stop using the program. The shareware registration entitles you to use this version of Transx as well as any future versions of the program that may or may not be released, subject to additional licensing conditions which may be attached. The commercial registration entitles you to receive the newest version of Transx and its companion programs, on a disk with a printed manual. Your registration key will always work with minor updates or bug-fix releases. (For example, upgrading from 1.0 to 1.2, but not 1.x to 2.x) Should if after you purchase Transx, a newer major version is released within 30 days, you will be entitled to receive a new registration key free of charge. If you require to upgrade to the new major version after this period, there will be a small upgrade fee. Registration will also you to use all of the available functions of Transx, and help to continue the development of this program. (not to mention maintain the legality of this agreement) By running any of the executable programs included, you agree that Pete Rocca, Darryl Olthoff, Multiboard Communications Centre nor any affiliates of the above mentioned are responsible for any damage or loss experienced, however so created. If you cannot agree to this, then your privilege to use any of these programs is revoked and it becomes illegal for you to execute any programs included with this documentation. You may freely copy and distribute the shareware version of Transx as long as its original archived contents are not modified in any way. You may NOT distribute any registration keys without the expressed written consent of Pete Rocca of Multiboard Communications Centre. You may not use a registration key that is not licensed to you by Pete Rocca, or any of the registration sites appointed by Pete Rocca. It is illegal to edit, alter, hack, reverse engineer and / or modify any components of Transx or its archive components in any manner. Transx and its encoding and security algorithims are the legal property of Multiboard Communications Centre. They may not be used in any other program other than Transx without the express written consent of Pete Rocca of Multiboard Communications Centre. This product, concept and design are protected by Canadian copyright laws and international treaty provisions. If dispute of any issues on legal grounds said above, then governing law of Ontario, Canada will rule. If you agree to all of the above, then you may use these programs. * REMEMBER THAT REGISTRATION IS QUITE INEXPENSIVE FOR ALL YOU SAVE *